Thanks Tom, and apologies for the confusion; not having worked w/gdb
before I was invoking it incorrectly. Here's what the core file
produced from the assertion failure has for a backtrace:
$ gdb ./bin/postgres data/core.20633
(gdb) bt
#0 0x00138eff in raise () from /lib/tls/libc.so.6
#1 0x0013a705 in abort () from /lib/tls/libc.so.6
#2 0x0820dc66 in ExceptionalCondition (
conditionName=0x6 <Address 0x6 out of bounds>,
errorType=0x5099 <Address 0x5099 out of bounds>, fileName=0x0,
lineNumber=492)
at assert.c:51
#3 0x081987bd in GetSnapshotData (snapshot=0x8303f04, serializable=0 '\0')
at procarray.c:514
#4 0x082293df in GetTransactionSnapshot () at tqual.c:1265
#5 0x081a8eb8 in PortalStart (portal=0x9b09a24, params=0x9b1c5dc,
snapshot=0x0)
at pquery.c:375
#6 0x081a6286 in exec_bind_message (input_message=0xbfffa2e0) at
postgres.c:1643
#7 0x081a7fb2 in PostgresMain (argc=4, argv=0x9aaa50c,
username=0x9aaa4e4 "joels")
at postgres.c:3205
#8 0x08182a45 in BackendRun (port=0x9ac8d58) at postmaster.c:2854
#9 0x08182529 in BackendStartup (port=0x9ac8d58) at postmaster.c:2498
#10 0x08180a57 in ServerLoop () at postmaster.c:1231
#11 0x0817fee5 in PostmasterMain (argc=3, argv=0x9aa8478) at postmaster.c:943
#12 0x08147a37 in main (argc=3, argv=0x9aa8478) at main.c:256
-Joel
